Task/store last measure #1670
Task/store last measure #1670
Conversation
|
Similar comment to the one at #1677 (comment) I'd suggest to make the last measure option to use the same approach that with another on/off features (eg. timestamp), that can be set at IOTA instance / group / device level, with the same precedence rules. |
|
Should this PR include tests cases regarding the new feature? |
doc/admin.md
Outdated
| If this flag is activated, last measure arrived to Device IoTAgent without be processed will be stored in Device under | ||
| lastMeasure field with in timestamp. This flag is disabled by default. |
There was a problem hiding this comment.
Maybe an example on how the measure is stored would be helpful. By the "will be stored in Device under
lastMeasure field with in timestamp" it is not fully clear (e.g. is a sub-JSON object used for that)?
Done in df26df1 |
Tests addresed in this other PR telefonicaid/iotagent-json#848 |
Co-authored-by: Fermín Galán Márquez <[email protected]>
Co-authored-by: Fermín Galán Márquez <[email protected]>
| #### `storeLastMeasure` | ||
|
|
||
| If this flag is activated, last measure arrived to Device IoTAgent without be processed will be stored in Device under | ||
| `lastMeasure` field (composed of sub-fields `timestamp` and `measure` for the measure itself, in multi-measure format). This flag is overwritten by `storeLastMeasure` flag in group or device. This flag |
There was a problem hiding this comment.
This flag is overwritten by
storeLastMeasureflag in group or device
Should api.md be modified to include the new field in the corresponding sections describing API payloads?
Co-authored-by: Fermín Galán Márquez <[email protected]>
Co-authored-by: Fermín Galán Márquez <[email protected]>
Co-authored-by: Fermín Galán Márquez <[email protected]>
#1669